-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get the integration tests up and running again #1300
Conversation
82db8d1
to
18db1cc
Compare
e4f5cea
to
9768db4
Compare
Ok, so it is now working, but the tests take forever: 23 minutes. There is a library called paratest that utilizes parallel testing, however the transaction isolation is not working at the moment (I have no idea why) so we have random assert failures with it (just tested it) |
Ok, so just checked what actually happens. It does not commit anything to the DB, however cahing is screwing us a little bit and the static settings were a problem. I am working on it :D |
If you need more php extensions installed. Let me know right. |
662a10d
to
dc7bd1a
Compare
- The messenger transactional wrap is not working with the tests, as it conflicts with the DoctrineTestBundle - Fix some type problems (DateTime vs DateTimeImmutable, nulls and initialization errors) - `SearchManager::findActivityPubActorsByUsername` now converts `!user@domain` into `@user@domain` so searching for a magazine by `!mag@domain` works from the API as well - The `StatsContentRepository` had a sign error - add a new docker compose for the test dependencies, as well as oauth keys for the tests - remove the purge user test, as this is no longer an option - change the .env.test to fit the new dependencies
- put the unit and functional tests in the same CI job - Fix the mention manager tests
dc7bd1a
to
319db5d
Compare
That is strange you need this kernel interface object while not using it? |
it is being passed to the parent which needs it to know in which environment it is |
the unit test job is required, but I renamed/removed it 😅 |
The domain changes from #1280 caused some tests to fail due to wrong assertions, fix that
Please don't rename integration tests to automated tests. You did so well. Why would you rename this? Unit tests and integration tests are two separate tests. I would like to see which fails from the PR perspective. |
Ok so your comment reads relatively offensive 😅 |
Ok Continue. I actually blame github. |
SearchManager::findActivityPubActorsByUsername
now converts!user@domain
into@user@domain
so searching for a magazine by!mag@domain
works from the API as wellStatsContentRepository
had a sign error